Skip to content

Make TextDocumentContentFeature a supported capability - #1796

Merged
Dirk Bäumer (dbaeumer) merged 1 commit into
mainfrom
dbaeumer/involved-catfish-coral
Jun 15, 2026
Merged

Make TextDocumentContentFeature a supported capability#1796
Dirk Bäumer (dbaeumer) merged 1 commit into
mainfrom
dbaeumer/involved-catfish-coral

Conversation

@dbaeumer

Copy link
Copy Markdown
Member

The TextDocumentContentFeature is now registered as a supported feature in the language client, reflecting its finalized status in the LSP specification. This change removes it from the proposed features namespace and integrates it into the core functionality of the client.

Fixes #1795

@dbaeumer
Dirk Bäumer (dbaeumer) enabled auto-merge (squash) June 15, 2026 14:31
@dbaeumer
Dirk Bäumer (dbaeumer) merged commit b0a8ea1 into main Jun 15, 2026
6 checks passed
@dbaeumer
Dirk Bäumer (dbaeumer) deleted the dbaeumer/involved-catfish-coral branch June 15, 2026 15:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

textDocumentContent capability/feature is still behind a proposed gate even though in 3.18 it's not flagged as proposed anymore

2 participants